"Title": "Which Version of RoboHELP Should I Use?",
"Symptoms": "RoboHELP 3.0\r\n· Use RoboHELP 3.0 if you have a 16 bit version of Microsoft Word (Word 2 or Word 6)\r\n· RoboHELP 3.0 will run under Windows 3.1/Windows 95/Windows NT 3.51\r\n· RoboHELP 3.0 will allow you to create Windows 3.1 help files.\r\n\r\nRoboHELP 4.0\r\n· Us RoboHELP 4.0 if you have Word 7.0.\r\n· RoboHELP 4.0 will run under Windows 95 and Windows NT 3.51\r\n· Will allow you to create either Windows 3.1 or Windows 95 help files",
"Resolution": "RoboHELP version 3.7 will allow you to create both Windows 3.1 and Windows 95 help files using Word 7. Version 3.7 is a free upgrade to RoboHELP 95 users. Contact Tech Support to receive the free upgrade.\r\n\r\nWhich type of help file do I need to create?\r\n· Windows 3.1 help files will run under Windows 3.1, Windows 95, and Windows NT. Windows 3.1 help files are compiled using either HCP.EXE or HC31.EXE.\r\n· Windows 95 help files will run under Windows 95 and Windows NT 3.51 and later. Windows 95 help files will not run under Windows 3.1. Windows 95 help files are compiled using HCW.EXE.",
"CreatedBy": 7814,
"CreatedOn": "02/04/97 10:28:11",
"UpdatedBy": 1,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "If you are planning on creating a Windows 3.1 help file and have RoboHELP 4.0, everyone else on the project should use RoboHELP 4.0 to edit that project. If some authors are still using RoboHELP 3.0, you should also use RoboHELP 3.0 to create and edit the project. All team members working on the project should be using the same version of RoboHELP.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1002,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Apostrophes and Quotes are Not Appearing",
"Symptoms": "As you type, Word replaces your apostrophes and/or quotes with \"smart-quotes\". The Microsoft 3.1 Help compiler does not understand the \"smart-quote\" symbol and ignores it.",
"Resolution": "RoboHELP 4.0\r\nGo to the Tools menu and select \"Fix Apostrophes and Quotes\".\r\n\r\nRoboHELP 3.0\r\nRoboHELP 3.0 can automatically fix this along with other incompatibilities between a Word generated RTF file and the Microsoft Help compiler. To turn on Automatic fixing up of RTF formatting, select Setup Project from the RoboHELP floating toolbar. Click on the Special tab and select Automatic fixing up of RTF formatting. Click OK. Now select Save As RTF from the RoboHELP floating toolbar. Once you recompile, your apostrophes and quotes will appear in the Help file. \r\nThis can also be fixed by turning off Smart Quotes and replacing the Smart Quotes in the document with Straight Quotes. From the Tools menu, select Auto Correct and uncheck: Change \"Straight Quotes\" to \"Smart Quotes\". \r\nNow you should find all of the \"Smart Quotes\" in your document and replace them with \"Straight Quotes\". Retype them or use Word's Find and Replace feature to do this for you.",
"CreatedBy": 7814,
"CreatedOn": "02/04/97 10:35:53",
"UpdatedBy": 1,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "As you type, Word replaces your apostrophes and/or quotes with \"smart-quotes\". The \"smart-quotes\" do not show up in the Help File. RoboHELP has a few options that can fix this problem.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1003,
"CategoryID": 0,
"NameID": 1,
"AreaID": 7,
"Title": "My Bullet Characters are a Strange Font",
"Symptoms": "This is a bug in the Microsoft Windows 95 help compiler. When using maximum (specifically Hall) compression, bullet characters that use a Wingding font are no longer bullets.",
"Resolution": "Use a Symbol font bullet, or use custom compression and do not select Hall compression, just Zeck compression.",
"CreatedBy": 7814,
"CreatedOn": "02/04/97 10:42:46",
"UpdatedBy": 1,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "When using maximum compression, bullet characters that use a Wingding font are no longer bullets.",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1004,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "My Double-Quote Characters Display As a Vertical Bar",
"Symptoms": "When using the MS Sans Serif font in a Windows 95 help file or the Helv font in a Windows 3.1 help file, \"typographical\" quote (curly quote) character appears as a vertical bar. \r\nThis occurs because the \"typographical\" quote is not available as a character in these fonts.",
"Resolution": "Use the Arial font instead of MS Sans Serif or Helv in your help projects. Or, replace all \"typographical\" quotes with \"straight quotes\". For more information about this, see Apostrophes and Quotes are Not Appearing.",
"CreatedBy": 7814,
"CreatedOn": "02/04/97 10:47:27",
"UpdatedBy": 11132,
"UpdatedOn": "02/06/97 17:14:15",
"Summary": "The \"typographical\" quote (curly quote) character appears as a vertical bar in the compiled help file.",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1005,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "What is Automatic Fixing Up of RTF Formatting?",
"Symptoms": "RoboHELP's \"Automatic fixing up of RTF formatting\" feature can fix inconsistencies between Word 6.0 and the Microsoft Help Compiler such as: \r\n· Hanging Indents not aligning properly (especially bulleted/numbered lists) \r\n· Apostrophes and Quotes not appearing in the compiled Help file \r\n· Hidden Paragraph warning messages \r\n· Revision text displaying in the compiled Help file \r\nTo turn on Automatic fixing up of RTF formatting, select Setup Project from the RoboHELP floating toolbar. Click on the special tab, and put a check in Automatic fixing up of RTF formatting. Click on OK. Now select Save As RTF from the RoboHELP floating toolbar. You will notice the message dialog box \"RoboHELP is Checking Formatting...\" with a percentage of completion.",
"Resolution": "What if I don't get the dialog box \"RoboHELP is Checking Formatting...\" after I click Save As RTF? \r\nAutomatic fixing up of RTF formatting needs to be turned on in two places in each document in your project in order for RoboHELP to check the RTF formatting of the document. First, make sure that Automatic fixing up of RTF formatting is turned on under Setup Project, as detailed above. Then, from the File menu, select Document Properties. Click the More... button. Verify that Automatic fixing up of RTF formatting is checked. Both boxes need to be checked in order for RoboHELP to check the RTF formatting of each document.",
"CreatedBy": 7814,
"CreatedOn": "02/04/97 10:52:32",
"UpdatedBy": 0,
"Summary": "RoboHELP's \"Automatic fixing up of RTF formatting\" feature can fix inconsistencies between Word 6.0 and the Microsoft Help Compiler.",
"VersionStart": "3",
"VersionEnd": "3"
},
{
"KBID": 1006,
"CategoryID": 0,
"NameID": 1,
"AreaID": 7,
"Title": "My Numbered Lists aren't Numbered in the Proper Order",
"Symptoms": "This is a bug in the Microsoft Windows 95 help compiler. The Microsoft Windows 95 help compiler no longer supports Auto-numbered lists. Microsoft's work-around is to number all of your lists by hand.",
"Resolution": "There is a style that ships with RoboHELP 4.00, \"Topic Text Numbered\", which works in most instances. Try applying this style to your numbered lists. If this doesn't work for your document, you will have to resort to Microsoft's solution of hand-numbering all numbered lists.",
"CreatedBy": 7814,
"CreatedOn": "02/04/97 10:56:08",
"UpdatedBy": 0,
"Summary": "The Microsoft Windows 95 help compiler no longer supports Auto-numbered lists. RoboHELP provides a style that should allow your numbered lists to work.",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1007,
"CategoryID": 0,
"NameID": 1,
"AreaID": 7,
"Title": "The First or Last Bullet is a Different Size",
"Symptoms": "In a bulleted list, the first or last bullet is a different size than the rest of the bullets, in the compiled help file. This is a bug in the Microsoft Windows 95 help compiler.",
"Resolution": "Use a \"fixed\" point bullet, or use the \"Topic Text Bulleted\" style that ships with RoboHELP 4.0.",
"CreatedBy": 7814,
"CreatedOn": "02/04/97 10:58:57",
"UpdatedBy": 0,
"Summary": "Due to a bug in the compiler, the first or last bullet in a bulleted list may be a different size.",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1008,
"CategoryID": 0,
"NameID": 1,
"AreaID": 7,
"Title": "Getting Bulleted/Numbered Lists and Hanging Indents to Align",
"Symptoms": "Hanging indents are recognized by the Microsoft 3.1 Help compiler only if there is a tab character at the same location as the From Left item in the Paragraph formatting.",
"Resolution": "RoboHELP 4.0\r\nGo to the Tools menu and select \"Fix Up Bullets and Numbered Lists\"\r\n\r\nRoboHELP 3.0\r\nRoboHELP 3.0 can automatically fix this for you. On the RoboHELP Tool palette, click Setup Project. Click the Special tab. Check \"Automatic fixing up of RTF formatting\". Click OK. If RoboHELP asks you if you want to turn on Automatic Fixing Up of RTF Formatting for every document in the Help Project, respond \"Yes\". Now click the \"Save as RTF\" button on the RoboHELP floating toolbar. You will notice the message \"RoboHELP is checking formatting\" and a percentage of completion. When you recompile your Help project, your hanging indents will align properly. \r\nAutomatic fixing up of RTF formatting will fix your problem 95% of the time. Another solution to try: highlight the entire list including any blank paragraphs before and after the list and apply the Normal Style to the list (go to the Format menu, select Style, highlight Normal, and click Apply). This will remove the bullets or numbering from the list. Now highlight just the list itself, not including any white space above or below the list. From the Format menu, Select Bullets and Numbering, and choose the bulleted/numbering style that you wish to use.",
"CreatedBy": 7814,
"CreatedOn": "02/04/97 11:01:39",
"UpdatedBy": 0,
"Summary": "How to get your bulleted lists, numbered lists, or hanging indents to align properly in the compiled help file.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1009,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "How to Jump From One Help File to Another?",
"Symptoms": "To jump from one help file to another, use the JumpId macro.\r\n1 Highlight the text you wish to use for your hotspot text.\r\n2 Go to the Insert menu and select Help Macro Hotspot.\r\n3 Click the Macro button in the lower right hand corner of the dialog.\r\n4 From the Choose a macro to Insert List, select the JumpId macro and click Insert.\r\n5 Click the browse button to select the HPJ file for the help file you wish to jump to.\r\n6 Select the context string of the Topic you wish to jump to and Click OK until you are back into your document.",
"Resolution": "Note: The HLP file that you are jumping to should be in the same directory as the original HLP file. If it is not, you need to modify the JumpId macro that RoboHELP creates for you and insert the full path to the help file. When specifying a path in a WinHelp macro, use two backslashes or a single forward slash for each backslash in the path.",
"CreatedBy": 7814,
"CreatedOn": "02/04/97 11:07:41",
"UpdatedBy": 0,
"Summary": "It is possible to jump from one help file to another, using the JumpId macro.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1010,
"CategoryID": 0,
"NameID": 1,
"AreaID": 9,
"Title": "The Index Tab Keywords from the Original Help File are Displayed After Jumping to a Help File",
"Symptoms": "When I jump from one help file to another using the JumpId macro, under Windows 3.1 the Search dialog lists the keywords for the new help file, but under Windows 95/NT, the keywords in the Index tab are those from the original help file. This is the behavior of the Windows 95 help viewer. It does not update the keywords when jumping to a new help file using the JumpId macro.",
"Resolution": "You could use the JumpKeyword macro, in place of the JumpId macro. This will force the keyword list of the new help file to be loaded. \r\nAlternatively, you can create a .CNT file for each related help file that includes a \":index\" statement for every other help file in the group. For example, assume we have three help files: a.hlp, b.hlp, and c.hlp. These three help files are linked using JumpId macros. In order to include the keywords from all three help files in the Index tab of any of the help files, use a text editor, such as notepad, to create a .CNT file for each one of the help files. Each .CNT file will contain a \":base\" statement, indicating which help file it belongs to, and a \":index\" statement for all other help file in the group. \r\n\r\nExample: a.cnt would contain:\r\n:base a.hlp\r\n:index b.hlp\r\n:index c.hlp",
"CreatedBy": 7814,
"CreatedOn": "02/04/97 11:11:13",
"UpdatedBy": 0,
"Summary": "When I jump from one help file to another using the JumpId macro, under Windows 3.1 the Search dialog lists the keywords for the new help file, but under Windows 95/NT, the keywords in the Index tab are those from the original help file. The Windows 95 help viewer does not update the keywords when jumping to a new help file using the JumpId macro.",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1011,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "How to Launch an Application or Document from my Help File?",
"Symptoms": "You can launch an application or a document from your help file by using a WinHelp macro. If you are creating a Windows 3.1 help project, use the ExecProgram macro. If you are creating a Windows 95 help project, use the ExecFile macro.",
"Resolution": "WinHelp 4.0 (Windows 95)\r\nUse the ExecFile macro.\r\n\r\nWinHelp 3.1\r\nUse the ExecProgram macro to jump from a help file to an application. The ExecProgram macro takes two parameters. The first is the command line that you wish to execute. This command line can be any command that can be executed from the File|Run command in File Manager in Windows 95 from the Start button|Run command. The second parameter of the ExecProgram macro should always be zero (other values will be ignored).",
"CreatedBy": 7814,
"CreatedOn": "02/04/97 11:18:52",
"UpdatedBy": 0,
"Summary": "You can launch an application or a document from your help file by using a WinHelp macro.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1012,
"CategoryID": 0,
"NameID": 1,
"AreaID": 8,
"Title": "Calling a Help File from a Visual C++ Application",
"Symptoms": "How do I call my help file from my Visual C++ application?",
"Resolution": "Using Visual C++ to call a help topic is easy. Use the WinHelp API function to call the topic of your choice. \r\nSee Also:\r\n WinHelp API function\r\n Adding \"What's This?\" Style help to a Visual C++ MFC application\r\n Trouble shooting my context-sensitive help file",
"Notes": "Again",
"CreatedBy": 1,
"CreatedOn": "02/04/97 11:24:19",
"UpdatedBy": 2,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "There are several topics describing how to add your Help File to a Visual C++ application.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1013,
"CategoryID": 0,
"NameID": 1,
"AreaID": 8,
"Title": "Pop-up Topics Display in Main Help Window in My Application",
"Symptoms": "I have defined my topics as pop-up's (or What's This? Topics), but when I display them as context-sensitive help topics from my application, they are appearing in the main help window, not as a pop-up. What window the help topics are displayed in from the application is determined by how the developer calls those help topics. The help author can not specify how a context-sensitive topic is displayed by the application.",
"Resolution": "What window the help topics are displayed in from the application is determined by how the developer calls those help topics. The help author can not specify how a context-sensitive topic is displayed by the application. You can not fix this, the developer must call the topics appropriately for them to appear in a pop-up window.\r\nThe book \"Mastering Windows 95 Help\", available in WinHelp Office and most bookstores, has a chapter on \"What's This?\" style help (chapter 5), that describes calling a \"What's This?\" topic from an application.",
"Notes": "New Note!",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:10:43",
"UpdatedBy": 2,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "I have defined my topics as pop-up's (or What's This? Topics), but when I display them as context-sensitive help topics from my application, they are appearing in the main help window, not as a pop-up.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1017,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Microsoft Word Error 1055: The Document Name or Path is Invalid",
"Symptoms": "When opening my RoboHELP project, I receive Microsoft Word basic error 1055: The document name or path is invalid. This indicates that Word can't find the RoboHELP templates.",
"Resolution": "From the Word Tools, click Options. Click the File Locations tab. Highlight User Templates, then click Modify. Note the location of the User Template directory. This should be c:\\winword\\template, c:\\msoffice\\templates, or something similar. If this is c:\\robohelp or anything other than where your other Word template (*.dot) files are located (referred to as your User Template directory), change it to point to your User Template directory, then exit RoboHELP and re-open the file.\r\nIf this is pointing to your User Template directory, make sure that you have the proper RoboHELP templates in your User Template directory. The easiest way to do this is to reinstall RoboHELP, and when RoboHELP prompts you to specify your Word Template Directory, make sure that you specify the User Template directory that is listed under Tools|Options|File Locations. \r\nYou could also search your system for the RoboHELP templates, and copy them into the User Templates Directory. Search your system for the file robohelp.dot. Go to the directory where the file is found. This directory should have four files in it (it may have more, but we are only interested in these four files): robohelp.dot, robortf.dot, rhexport.dot and robodocs.dot. \r\nNote: If you are using RoboHELP 4.00a, there will be two additional files, robohp31.dot and robort31.dot. Copy these files as well.\r\nCopy these four files to the User Template Directory specified under Tools|Options|File Locations.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:14:18",
"UpdatedBy": 11132,
"UpdatedOn": "02/06/97 17:18:26",
"Summary": "When opening my RoboHELP project, I receive Microsoft Word basic error 1055: The document name or path is invalid.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1019,
"CategoryID": 0,
"NameID": 1,
"AreaID": 11,
"Title": "The Compiler Never Returns from the \"Making Help Project..\" Dialog",
"Symptoms": "If the compiler never returns from the \"Making Help project, please wait.\" dialog, the Microsoft help compiler has failed. This is usually caused by an invalid or a root directory in the BMROOT option in the [OPTIONS] section of the project (.HPJ) file.",
"Resolution": "Remove any invalid or root (i.e. C:\\ or A:\\) directories from the BMROOT statement. Go into project setup, click on the Settings tab, click on the Graphics button. Highlight any invalid or root directories that are listed under selected directories, and click Remove.\r\n\r\nThese symptoms can also occur occasionally when running RoboHELP 3.0 under Windows 95. Try the following:\r\n1 Click the \"Make Project\" button,\r\n2 Click the \"Configure\" tab in the Make Project dialog.\r\n3 Put a check in \"Full screen DOS box using RHHCFS.PIF.\r\n4 Click the Make Project tab, then click Make.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:18:25",
"UpdatedBy": 2,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "When attempting to compile my RoboHELP project, but the compiler never returns from the \"Making Help project, please wait.\" dialog.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1020,
"CategoryID": 0,
"NameID": 1,
"AreaID": 11,
"Title": "Help Compiler Error 1079: Out of File Handles",
"Symptoms": "The compiler does not have enough available file handles to continue the build, therefore the Microsoft Help compiler does not compile the Help file.",
"Resolution": "Increase the FILES setting in the CONFIG.SYS file to Files=80. If it is already set to 80 or above raise it to 120 or higher (it can be as high as 255). Then reboot your computer and recompile.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:20:43",
"UpdatedBy": 2,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "The compiler does not have enough available file handles to continue the build.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1021,
"CategoryID": 0,
"NameID": 1,
"AreaID": 11,
"Title": "Help Compiler Error 1100: Cannot Open File, Permission Denied",
"Symptoms": "You do not have the required file privileges to open the requested file. Requested files must have at least read privilege to be opened. \r\nResult: The Microsoft Help compiler ignores the file.",
"Resolution": "One of the following:\r\n· You need to have both the TEMP and TMP environmental variables SET in your AUTOEXEC.BAT file to a writeable, non-root directory. It can not point to a root directory such as c:\\ or a:\\. It must point to a valid directory.\r\n· Your FILES= statement in CONFIG.SYS should be between 80-128. You may need to make it even higher (it can be as high as 255). \r\n· Another possible cause of the 1100 error is low system resources. Try exiting windows, rebooting your computer and re-compiling. \r\n· Another reason could be that the file is already open. Try renaming the filename.HLP file to filename.OLD. If you can't rename the HLP file in File Manager, it is either open or read-only. The Microsoft Help Compiler will not proceed if it cannot delete the old Help file. Unlock the file and then recompile. \r\n· Change your access privileges if you are working on a secured network, or change the file attributes to read only or read/write.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:23:02",
"UpdatedBy": 2,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "I am receiving Microsoft Help Compiler Error 1100: Cannot open file, permission denied.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1022,
"CategoryID": 0,
"NameID": 1,
"AreaID": 11,
"Title": "Help Compiler Error 2331: Context number already used in [MAP] section.",
"Symptoms": "Microsoft Help Compiler Error 2331: Context number already used in [MAP] section is caused by an entry in one of your map files that uses a map number that has already been used for a different topic in the project. This can be caused by having any character other than A-Z, a-z, 0-9 or the underscore \"_\" character in your context strings. Check for periods or other invalid characters in the context strings. Illegal characters in the context string of a topic will cause the RoboHELP automatic map file generator to duplicate those topics in the .HH file.",
"Resolution": "If you have any topics with invalid characters, edit the topics and remove those invalid characters.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:24:34",
"UpdatedBy": 2,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "I am receiving Microsoft Help Compiler Error 2331: Context number already used in [MAP] section.",
"Symptoms": "Microsoft Help Compiler Error 2550: Invalid path. The BMROOT statement is what is used to tell the Microsoft help compiler where to find your graphics. It must not contain any invalid directories or any root directories (i.e. C:\\, A:\\ etc.)",
"Resolution": "Go into Project Setup, click the Settings tab, click \"Graphics\". Highlight any invalid or root directories that are listed under \"Selected Directories\" and click \"Remove\".",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:26:27",
"UpdatedBy": 0,
"Summary": "I am receiving Microsoft Help Compiler Error 2550: Invalid path.",
"Symptoms": "Microsoft Help Compiler Error 4011: Context string already used is caused by two or more topics in the help project having the same context string. This is generally caused by making topics out of the same words. RoboHELP automatically suggests the context string of topic to be the topic title. Two topics may have identical titles and search keywords, but the context string must be unique.",
"Resolution": "The easiest way to locate the problem is to use the error locator to take you to the first topic that uses this context string. Put your cursor in the topic title (don't highlight anything, though) and click \"Edit\" on the floating toolbar. This will bring the \"Edit Help Topic\" dialog. Change the context sting by putting a \"2\" after it (no spaces). Click OK and when RoboHELP asks you to \"Search and Replace old context string with new one\" (this is a paraphrase), click cancel. Now \"Save as RTF\", to update the context string list. Use the Goto topic button (it should now list both topics) and go to the other topic that uses the same context string. Decide which on you want to keep and delete the other, making sure that you change the context string back if it's the topic that you modified.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:27:41",
"UpdatedBy": 0,
"Summary": "I am receiving Microsoft Help Compiler Error 4011: Context string already used.",
"Symptoms": "Microsoft Help Compiler Error 4031: Invalid context string. This happens when the context string footnote contains non-alphanumeric characters or is empty. \r\nResult: The Microsoft Help compiler does not assign the topic an identifier.",
"Resolution": "This is usually found when there is a hotspot on a SHG file to which no context string is assigned. Open the SHG file in the SHED editor. From the Edit menu, click Select. This will list all of the hotspots that have been created. Select the hotspots, one by one, until you find one without an associated context string. Click Select. This will take you back into your SHG graphic with the hotspot highlighted. (Note: if the hotspot is very small, it might appear that nothing is highlighted. Don't worry, it is highlighted.) Now press the Delete key. This will delete the hotspot. Choose File|Save, then File|Exit. Now recompile. (Note: you do not have to reinsert the SHG graphic into the document, recompiling is sufficient to fix the error.)",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:28:59",
"UpdatedBy": 0,
"Summary": "I am receiving Microsoft Help Compiler Error 4031: Invalid context string.",
"Symptoms": "Microsoft Help Compiler Error 4056: Unresolved context string specified in Contents option indicates that the Contents topic defined in the Help project file could not be found. As a result, the Microsoft Help compiler uses the first topic in the build as the Contents.",
"Resolution": "Click Setup Project on the RoboHELP floating toolbar. Click Contents. Select the context string of the topic that you wish to use for the Contents topic. Click OK then recompile.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:34:12",
"UpdatedBy": 0,
"Summary": "I am receiving Microsoft Help Compiler Error 4056: Unresolved context string specified in Contents option.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1027,
"CategoryID": 0,
"NameID": 1,
"AreaID": 11,
"Title": "Help Compiler Error 4113: Unresolved jump or popup.",
"Symptoms": "Microsoft Help Compiler Error 4113: Unresolved jump or popup indicates that you have a jump or a popup in the topic identified that is pointing to an invalid topic.",
"Resolution": "Use the RoboHELP error locator to take you to the topic that contains the unresolved jump or topic. The context string of the unresolved jump will be listed in the error message. Search the topic for a jump or popup in the topic that points to the context string that is listed. Edit the hotspot (by placing your cursor on the green text and selecting \"Help Hotspot…\" from the Edit menu) and point it to a valid topic.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:35:58",
"UpdatedBy": 0,
"Summary": "I am receiving Microsoft Help Compiler Error 4113: Unresolved jump or popup.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1028,
"CategoryID": 0,
"NameID": 1,
"AreaID": 11,
"Title": "Help Compiler Error 4652: Table formatting too complex.",
"Symptoms": "Microsoft Help Compiler Error 4652: Table formatting too complex. The Microsoft help compiler does not support anything other than basic table formatting. The Microsoft help compiler does not support borders in tables, shading in tables, tables which have cells that are more than a single column and a single row, and certain paragraph justification formatting inside of tables.",
"Resolution": "Remove the formatting from the table that is causing the warning. Or, ignore the warning. The Microsoft help compiler is notifying you that you are using formatting that it doesn't support. It will not display this formatting, but your help file will run without errors.\r\n\r\nNote:To include tables that contain complex formatting (i.e. borders, shading, etc.) in your help file, take a screen capture of the table inside of Word, and insert the bitmap of the table into your help project.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:37:05",
"UpdatedBy": 0,
"Summary": "I am receiving Microsoft Help Compiler Error 4652: Table formatting too complex.",
"Symptoms": "Microsoft Help Compiler Error 4753: Hidden Paragraph indicates that a paragraph marker is part of the hidden text. As a result, the compiler ignores the paragraph marker formatted as hidden text, so the two paragraphs will run together.",
"Resolution": "1 Open the Help document (.DOC) that is generating this error message.\r\n2 Go to the top of the document (Ctrl+Home). Select the Edit|Find menu (Ctrl+F).\r\n3 Click the Special button and select Paragraph Mark. \r\n4 Click the Format button, select Font, and put a check in Hidden. Click OK. \r\n5 Click Replace. \r\n6 Click the Special button and select Paragraph Mark. \r\n7 Click the Format button, select Font, and then check Hidden, then uncheck Hidden. Hidden should be cleared out, not grayed out and not checked. Click OK. \r\n8 The Replace dialog box should say:\r\n {bmc REPLACE.shg}\r\n9 Click Replace All. Word will tell you how many replacements it made. If Word asks you if you want to continue from the top of the document, choose OK. \r\n10 Recompile.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:40:33",
"UpdatedBy": 0,
"Summary": "I am receiving Microsoft Help Compiler Error 4753: Hidden Paragraph.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1035,
"CategoryID": 0,
"NameID": 1,
"AreaID": 11,
"Title": "Help Compiler Error 4792: Non-scrolling region defined after scrolling region.",
"Symptoms": "Microsoft Help Compiler Error 4792: Non-scrolling region defined after scrolling region indicates that you have text formatted with the \"Keep with next\" paragraph formatting attribute that is not the first paragraph in the topic.",
"Resolution": "Highlight the entire topic, beginning with the page break and ending just above the next page break. From the Format menu, select Paragraph, click the \"Text Flow\" tab, and make sure \"Keep with next\" is clear, not gray and not checked.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:42:07",
"UpdatedBy": 0,
"Summary": "I am receiving Microsoft Help Compiler Error 4792: Non-scrolling region defined after scrolling region.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1040,
"CategoryID": 0,
"NameID": 1,
"AreaID": 11,
"Title": "Help Compiler error 5059: Not Enough memory to build help file.",
"Symptoms": "Microsoft Help Compiler error 5059: Not Enough memory to build help file indicates that the Microsoft Help compiler does not have enough memory to complete the build process. As a result, the compiler does not create a help file.",
"Resolution": "Try one or all of the following: \r\n· Use HCP.EXE as the Help compiler. \r\n· Make sure all graphics are included by reference {bmx *.bmp} using RoboHELP's Insert Graphic Tool. \r\n· Make sure all graphics are 16 colors or less. \r\nThis error is most frequently caused by bitmaps that are greater than 16 colors. To determine if it is the bitmaps that are causing the problem, copy all of the graphic files (.bmp's, .shg's, and .wmf's) to a different directory and recompile. If the project compiles without generating a 5059 error message, the problem is one or more of the graphics are greater than 16 colors. Open the bitmaps up in Windows Paintbrush (or Paint) and do a File|Save As and change the type to 16 color bitmap.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:45:13",
"UpdatedBy": 0,
"Summary": "I am receiving Microsoft Help Compiler error 5059: Not Enough memory to build help file.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1045,
"CategoryID": 0,
"NameID": 1,
"AreaID": 10,
"Title": "My Graphics Look Distorted",
"Symptoms": "When viewing a Windows 3.1 help files in different screen resolution, the graphics appear very distorted; sometimes very large, sometimes very small. The Windows Help viewer looks at the resolution that a graphic was originally created in. When displaying that graphic, if the current display device has a different resolution, it will try to stretch or shrink the graphic, so that it appears approximately the same size as when it was created. When bitmaps are stretched or reduced, the graphics look distorted.",
"Resolution": "Convert all graphics to .SHG files and use shgrez.exe on them.\r\nFirst, convert all graphics to .SHG files by opening the graphic in the SHED Enhanced Hotspot editor. Then go to the File menu, select Save As, and give it the same filename with the extension .SHG.\r\nSecond, use the program SHGREZ.EXE. It is a freeware utility that allows you to strip the aspect ratio from a .SHG file (it only works on .SHG files, that is why you need to convert the graphic to an .SHG file first). Copy SHGREZ.EXE to your RoboHELP directory and double click on it in File Manager to execute it. Navigate to the directory that contains your new .SHG files, select them all, select the radio button for \"No Scaling Information\", and click Adjust. \r\nNow use these .SHG files in your project instead of the original graphic files.\r\n\r\nNote:The Microsoft Windows 95 help compiler automatically strips scaling information from bitmaps at compile time. These graphics will always display correctly.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:47:23",
"UpdatedBy": 3,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "When I am viewing my help file on computers that have different size monitors, the graphics look distorted.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1050,
"CategoryID": 0,
"NameID": 1,
"AreaID": 10,
"Title": "What Types of Graphic Files Can I Use?",
"Symptoms": "What types of graphic files can I use in my help projects? The answer depends on the targeted Help compiler.",
"Resolution": "WinHelp 3.1\r\nThe Microsoft Windows 3.1 help compiler supports bitmaps (.shg files), windows metafiles (.WMF files) and segmented hypergraphics (.SHG files) created from either bitmaps or windows metafiles. All graphics in your Windows 3.1 help project must be 16 colors or less.\r\nNote: To use 256 color graphics in your Windows 3.1 help file, use must use the hlp256.dll that comes with RoboHELP 3.0. See How do I use 256 color graphics in my Windows 3.1 help file? \r\n\r\nWinHelp 4.0 (Windows 95)\r\nThe Microsoft Windows 95 help compiler supports bitmaps (.shg files), windows metafiles (.WMF files) and segmented hypergraphics (.SHG files) created from either bitmaps or windows metafiles. The graphics can be of any color depth. \r\nNote: If you are using graphics of 256 color or higher, see the information about palette conflicts: My graphics colors are shifting.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:49:15",
"UpdatedBy": 0,
"Summary": "What types of graphic files can I use in my help projects?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1055,
"CategoryID": 0,
"NameID": 1,
"AreaID": 10,
"Title": "Converting Graphics from One Fromat to Another",
"Symptoms": "How can I convert graphics from one format to another?",
"Resolution": "Use PaintShop Pro. PaintShop Pro allows you to easily convert from many popular graphics formats into either bitmaps or windows metafiles. PaintShop Pro is available as part of Blue Sky Software's Web Office, the complete Web Authoring Solution.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:51:11",
"UpdatedBy": 0,
"Summary": "How can I convert graphics from one format to another?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1060,
"CategoryID": 0,
"NameID": 1,
"AreaID": 10,
"Title": "How do I Resize My Graphics?",
"Symptoms": "How do I resize my graphics so my screen captures do not have scroll bars?",
"Resolution": "Use PaintShop Pro. PaintShop Pro allows you to easily convert from many popular graphics formats into either bitmaps or windows metafiles. PaintShop Pro is available as part of Blue Sky Software's WebOffice, the complete Web Authoring Solution.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:52:29",
"UpdatedBy": 0,
"Summary": "How do I resize my graphics so my screen captures do not have scroll bars?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1062,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Unable to Open Specified Library (Error 543 or 582)",
"Symptoms": "Receiving a Word basic Error 543 (Word 6.0), or Word BASIC error 582 (Word 7.0): Unable to open specified library may be due to using old RoboHELP templates with a newer version of RoboHELP. If you had previously installed RoboHELP on your machine, make sure that the templates in your Word User Template directory are the correct RoboHELP templates. See Word basic error 1055: The document name or path is invalid for more information about making sure you are using the correct version of the templates.\r\nAlso, some virus protection programs that run in the background can interfere with the loading of certain DLL's. All such virus protection programs should be commented from the autoexec.bat file and run regularly a different way.",
"Resolution": "Also, the Word \"Prank\" macro virus scan modifies the normal.dot file which prevents RoboHELP from loading without using the starter application. Load all RoboHELP documents using the RoboHELP starter application. Alternately, you could rename your normal.dot template, in your Word User Template Directory. Word will automatically recreate your normal.dot template, without the macros that prevents RoboHELP from loading when double clicking on a DOC file. \r\nNote: This will disable virus protection and is not recommended as a long term solution. Make sure to reapply scanprot.dot, and the RoboHELP fix macrofix.dot, to protect against future virus infection.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:53:31",
"UpdatedBy": 0,
"Summary": "I am receiving a Word basic Error 543 (Word 6.0), or Word BASIC error 582 (Word 7.0): Unable to open specified library.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1064,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Popup Topics Shor Only the Topic Title",
"Symptoms": "When I display my popup topics, they only show the topic title. This happens when the topic has a non-scrolling region defined. Topics with a non-scrolling region, when displayed in a pop-up window, only display the topic title.",
"Resolution": "Highlight the entire topic, beginning with the page break and ending with the paragraph mark just before the next page break. From the Format menu, select Paragraph then click the Text Flow tab. Uncheck the Keep With Next box. Click OK.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 12:58:11",
"UpdatedBy": 0,
"Summary": "When I display my popup topics, they only show the topic title.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1066,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "New Topic Not Listed in the Create Jump Dialog",
"Symptoms": "Newly created topics are not listed in the Create Jump dialog. This happens because RoboHELP updates the topic list when you save the file as an RTF file.",
"Resolution": "Click on Save As RTF on the RoboHELP floating toolbar. The topic will now be available for creating jumps. \r\nIt is also possible that the context string buffer is full. A large Help document with long context strings can fill this buffer. If your Help document has over 400 topics, or if the context strings are extremely long, break the project into two or more DOC files. \r\nSee also: How large can my help project be? How many topics should I have in each DOC file?",
"CreatedBy": 1,
"CreatedOn": "02/04/97 13:00:06",
"UpdatedBy": 0,
"Summary": "I just created a topic, but it's not available in the Create jump dialog.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1068,
"CategoryID": 0,
"NameID": 1,
"AreaID": 8,
"Title": "Including the MAP File from Development in my RoboHELP Project",
"Symptoms": "How do I include the map file from the development team in my RoboHELP project?",
"Resolution": "· Copy the map file from your development team into your RoboHELP project directory.\r\n· Inside of your RoboHELP project, go into Project Setup, click the Advanced tab, and double click on the MAP section. The map file will be listed in the upper left hand window in the \"Choose Files For\" dialog. Select it and click Add. It will be added under \"Selected Files\" in the lower window. Click OK.\r\n· Create your overview and procedural help topics. We will connect these topics with the map file using the alias section of the HPJ file, with the help of the RoboHELP Contents Tab Composer.\r\n· To create new \"What's This?\" style topics:\r\n1 Click the \"Create Popup\" button and select the \"New What's This?\" tab, creating a context-sensitive topic to display in a What's This? style popup window\r\n2 Click Choose.\r\n3 The Choose Topic ID Provided by Development Team dialog box appears.\r\n4 Click Browse to select a map file. \r\n5 Select the correct Topic ID.\r\n6 Click OK.\r\n7 Enter the definition text for the Help topic in the space provided.\r\n8 Click OK.\r\nTIP: If possible, place all context-sensitive Help topics in one document. This means that you can use the automatic map file generation for the entire Help document. This saves time in creating or assigning specific map numbers for all context-sensitive topics within various Help documents. \r\n\r\nNote: What's This? style topics do not generally have a ? character contained in their footnotes. Instead, these topics contain only the # character.\r\n· Copy the HLP file to the same folder as your application.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 13:02:59",
"UpdatedBy": 0,
"Summary": "How do I include the map file from the development team in my RoboHELP project?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1070,
"CategoryID": 0,
"NameID": 1,
"AreaID": 1,
"Title": "Moving or Renaming a Help Project",
"Symptoms": "I need to rename or move my help project, what do I do?\r\nCAUTION:If the project document of the Help project you wish to rename is open, close it before proceeding with the steps outlined below. Making a backup of your project would also be a good idea.",
"Resolution": "1. In the Windows Explorer, make the project directory the current directory. Do the following:\r\n· Select the project document.\r\n· Click Rename from the File menu.\r\n· Edit the name as desired.\r\n· Repeat for all files in the project.\r\n2. Optional step to rename the project directory. Do the following:\r\n· Select the directory containing the project document. \r\n· Click Rename from the File menu.\r\n· Edit the name as desired.\r\n3. Open the Windows NOTEPAD program with the <newname>.RBH file.\r\n4. Under the heading [Document Files] locate the line containing the text <oldname>.DOC=1, and change the text which reads <oldname> to <newname>.\r\n5. Open the project document in a Word session.\r\n6. Click Setup from the Project menu.\r\n7. Select the Settings tab.\r\n8. Click Document.\r\n9. The project document (having been renamed) will not be visible in Select File. You should add the renamed project document to the list. For more information about adding document files to a project, see Adding a Help document to a Help project \r\n10. If you are using automatic map file generation, you need to remove the map file containing the <oldname>.HH file and add the map file named <newname>.HH. See About Map Files for details.\r\n· Click Setup Project.\r\n· Select the Advanced tab.\r\n· Under Setup Section, double-click [MAP] Include Files.\r\n· Under Selected Files, highlight the <oldname>.HH file and click Remove.\r\n· Under Choose Files for, highlight the <newname>.HH file and click Add.\r\n· Click OK to accept your changes.\r\n11. Open the new .CNT file in notepad, and change the :Base statement (the first line in the CNT file) so that it uses the new name of the HLP file.\r\n12. There is a hidden/system file in your project directory with the same file name as your HLP file, and the extension GID. Delete this file and run the help file again.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 13:04:45",
"UpdatedBy": 3,
"UpdatedOn": "02/06/97 17:15:46",
"Summary": "I need to rename or move my help project, what do I do?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1075,
"CategoryID": 0,
"NameID": 1,
"AreaID": 2,
"Title": "Importing an Existing Word Document",
"Symptoms": "How do I import an existing Word document into my RoboHELP project?\r\n1 Make a copy of the document that you want to convert to a help document. Put this copy in the same directory as your RoboHELP project.\r\n2 Open your RoboHELP project. From the Tools menu, select Import Documentation.\r\n3 Select the document that you want to import.\r\n4 Accept the default values in the Import existing document dialog. For more information, see the RoboHELP written documentation about converting existing documentation.",
"Resolution": "Common Pitfalls in Converting Documents\r\n\r\nThe user does not make a copy of the original document. \r\nDuring the conversion process, the Word document becomes a RoboHELP document. If you wish to preserve the original document, make a copy before importing the document into RoboHELP.\r\nThe user converts the document, but no new topics are created. \r\nThe document being converted must use Word styles, such as Heading 1, Heading 2, etc., to be automatically turned into help topics during conversion. If all of the text in your original Word document uses the same Word style, such as normal, RoboHELP can not automatically create topics for you. Highlight the text that is the topic title, click \"New Topic\" on the floating toolbar, and click OK to create new help topics.\r\nThe document is converted and the topics were created. I can see the footnote codes. But when I run the help file, it's blank.\r\nThe help topics were created, but no jumps to them are automatically created. To do this, first save the imported document as an RTF file. Then go to the main document, the one with the same name as the .HPJ file. Create a Topic, if one does not already exist, and name it Contents. \r\n From the Insert menu, select Help Index…\r\n From the Tools menu, select Autocreate Hotspot List…\r\nIn the file box, select the name of the imported document. Leave the other defaults and click OK.\r\nA jump will be created to every topic in the imported document for you automatically. Recompile and test the project.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 13:06:08",
"UpdatedBy": 11031,
"UpdatedOn": "02/06/97 16:04:00",
"Summary": "How do I import an existing Word document into my RoboHELP project?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1077,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "When Compiling, I am Prompted to Select the Current Project",
"Symptoms": "While working on your project, you keep getting a message asking you to select a current project.",
"Resolution": "One or more of the DOC files in your project are attached to the wrong template. The main DOC file (the one with the same name as the HPJ file) must be attached to the robohelp.dot template. All other DOC files in the Help project must be attached to the robortf.dot template. To attach a template, from the File menu, choose Templates and click the Attach button. \r\nNote:If you are using RoboHELP 4.00a and creating a Windows 3.1 help project, the main document will be attached to robohp31.dot and all subordinate documents are attached to robort31.dot.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 13:08:19",
"UpdatedBy": 0,
"Summary": "When I compile my help project, RoboHELP tells me there is no current project and prompts me to select an HPJ file.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1081,
"CategoryID": 0,
"NameID": 1,
"AreaID": 4,
"Title": "RoboHELP Behaves Strangely After Installing Virus Protection",
"Symptoms": "The Word macro virus protection tool from Microsoft, scanprot.dot, can prevent your RoboHELP documents from loading normally. This is because scanprot.dot disables any startup macros in the document when the document is loaded. RoboHELP documents use startup macros to give them the RoboHELP functionality.",
"Resolution": "Download and install macrofix.dot, the RoboHELP fix to the Microsoft Virus protection tool. This will leave the Microsoft virus protection in place, while allowing your RoboHELP documents to open normally.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 13:12:59",
"UpdatedBy": 2,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "I installed the Microsoft Word Macro Virus protection tool (scanprot.dot), but now my RoboHELP project is behaving strangely.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1083,
"CategoryID": 0,
"NameID": 1,
"AreaID": 4,
"Title": "Modifying the RoboHELP Templates",
"Symptoms": "The RoboHELP templates can be modified the same way other Word templates can be modified. You can add new styles to the templates, or modify existing styles using Format|Style. You can also copy styles from one template to another using the Microsoft Word Style Organizer. Here are some things to keep in mind when modifying the RoboHELP templates.",
"Resolution": "1. Always make a backup of the RoboHELP templates before modifying them, some if you add something to the template that effects the performance of RoboHELP, you can go back to the original template.\r\n2. It is OK to add, remove and modify document styles in the RoboHELP templates.\r\n3. You should avoid adding custom macros to the RoboHELP templates. Because of the tight integration required between RoboHELP and Microsoft Word, any macros that you might add to the RoboHELP templates could effect RoboHELP, potentially disabling some of RoboHELP's functionality.\r\n4. If you make a modification to one of the RoboHELP templates, the same modification should be made to the other RoboHELP template.\r\nSee Also:Which RoboHELP template should be attached to my document?",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:14:42",
"UpdatedBy": 3,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "I need to modify my RoboHELP templates. What's the best way to do this?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1085,
"CategoryID": 0,
"NameID": 1,
"AreaID": 2,
"Title": "Hourglass Remains Onscreen While Importing Documentation",
"Symptoms": "I am importing existing documentation, or using the Tools Conversion option, but the hour glass has been on my screen for more than a minute, and it appears that nothing is happening. The Microsoft Word screen update is turned off. When you press escape, RoboHELP corrects the problem by turning it back on.",
"Resolution": "Press the ESC key, and then the conversion will continue and complete normally.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:15:37",
"UpdatedBy": 11031,
"UpdatedOn": "02/06/97 16:04:31",
"Summary": "I am importing existing documentation, or using the Tools|Conversion option, but the hour glass has been on my screen for more than a minute, and it appears that nothing is happening.",
"VersionStart": "3",
"VersionEnd": "3"
},
{
"KBID": 1087,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "QuickCheck Errors 9055: Hotspot Text Crosses Paragraph Boundary",
"Symptoms": "The Quick Check Errors feature is more sensitive/critical than the Microsoft help compiler. The \"9005: Hotspot text crosses paragraph boundary\" can be ignored if the Microsoft Help compiler doesn't give you any corresponding errors.",
"Resolution": "If the Quick Check Errors reports this error, but when you actually compile you don't get any errors then you may ignore the error.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:17:15",
"UpdatedBy": 0,
"Summary": "When I do a check of my project, I receive error 9005: Hotspot text crosses paragraph boundary. When I compile, I receive no errors.",
"VersionStart": "3",
"VersionEnd": "3"
},
{
"KBID": 1089,
"CategoryID": 0,
"NameID": 1,
"AreaID": 10,
"Title": "Replacing the Underlying Graphic in a SHG File",
"Symptoms": "Is there an easy way to replace the underlying graphic in my SHG file and still keep my hotspots? Yes.",
"Resolution": "Copy the graphic that you want to use to replace the underlying graphic to the clipboard. Edit the .SHG file using the SHED editor, go to the Edit menu, and select replace. This will replace the underlying graphic in the .SHG file with the graphic that was copied to the clipboard.\r\nNote: There is no way to get the underlying graphic out of a SHG file, except by doing a screen capture of the SHG file from the SHED editor.",
"Notes": "Try again",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:19:32",
"UpdatedBy": 0,
"UpdatedOn": "02/06/97 15:53:09",
"Summary": "Is there an easy way to replace the underlying graphic in my SHG file and still keep my hotspots?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1091,
"CategoryID": 0,
"NameID": 1,
"AreaID": 10,
"Title": "Jumping From a SHG Graphic to a Secondary Window",
"Symptoms": "How do I jump from a SHG graphic to a secondary window? Use the JumpId macro, and then specify that you want the topic to be displayed in the secondary window.",
"Resolution": "1 Create your hotspot in the SHED editor, and double click it to bring up the Enhanced Hotspot Attributes dialog.\r\n2 Change Type to macro, click Choose.\r\n3 From the Choose a macro to Insert List, select the JumpId macro and click Insert.\r\n4 Select the context string of the Topic you wish to jump to and Click OK until you are back into the Enhanced Hotspot Attributes dialog.\r\n5 Modify the JumpId macro that is created for you by putting a \">\" and the name of the secondary window you want the topic displayed in after the help file name. \r\n Example: JumpId(\"GENERIC.HLP>gloss\",\"Glossary\")\r\n\r\nSee also: Running a macro from the CNT tab or the SHED editor",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:21:10",
"UpdatedBy": 0,
"UpdatedOn": "02/06/97 15:56:41",
"Summary": "How do I jump from a SHG graphic to a secondary window?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1095,
"CategoryID": 0,
"NameID": 1,
"AreaID": 1,
"Title": "I Can't Remove a Document From My Project",
"Symptoms": "Deleting a document from your directory does not automatically remove it from your project.",
"Resolution": "Go into Project Setup. Click the Advanced tab. Double click on the [FILES] section. Highlight the RTF file associated with the document that you removed from the project and click remove. Click OK. Now, still in the Advanced tab in Project setup, double click on the [MAP] section. Verify that there is no .HH file listed under selected files with the same name as the document that you removed. If one is listed, highlight it and click remove.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:22:45",
"UpdatedBy": 0,
"Summary": "I deleted the DOC file in my project from my project directory, and now I can't remove the document from my project. How do I remove it?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1097,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "What are Build Tags?",
"Symptoms": "Buildtags are supported in RoboHELP by specifying a build tag (denoted by the \"*\" footnote) on a topic by topic basis. Build tags are used in conjunction with the [BUILDTAGS] section of the .HPJ file and the BUILD option in the [OPTIONS] section of the .HPJ file to specify which topics you wish to include in or exclude from a particular help file build. Build tags can be specified for a particular topic in the Edit Help Topic dialog box (by clicking Edit on the floating tool bar.) All build tag footnotes must be listed in the [BUILDTAGS] section. The BUILD expression is used to specify which topics to include/exclude. See the following documentation from HCW.EXE online help for more details.",
"Resolution": "===== From HCW.HLP =====\r\n[BUILDTAGS] section in the HPJ file\r\n\r\n[BUILDTAGS]\r\ntag\r\n\r\nThe [BUILDTAGS] section defines the valid build tags for a Help file. Help Workshop uses the build tags to determine which topics to include or exclude when building the Help file.\r\nThis section is used in conjunction with the build tag footnote (*) and the BUILD option. The build tag footnote associates a particular build tag with a given topic. If the build tag is included in the [BUILDTAGS] section and defined in the BUILD expression, Help Workshop compiles the topic; otherwise, it excludes the topic from the build.\r\n\r\nParameter - Description\r\n\r\ntag - Specifies a build tag consisting of any combination of characters except spaces. Help Workshop strips any spaces it finds between the start of the build tag and the end of the tag. Build tags are case insensitive, so Help Workshop treats uppercase and lowercase characters as the same. Each build tag can have as many as 32 characters.\r\n\r\nComments\r\n\r\nThe Help Workshop interface does not provide a way to modify the [BUILDTAGS] section in your project file. To create or modify a [BUILDTAGS] section, load the project file into a text editor, and then add or edit the section.\r\n\r\nExample\r\n\r\nThe following example defines four build tags in a sample project file:\r\n\r\n[BUILDTAGS]\r\nDEMO ;topics to include in demo build\r\nMASTER ;topics to include in master Help file\r\nDEBUGBUILD ;topics to include in debugging build\r\nTESTBUILD ;topics to include in a mini-build for testing\r\n\r\nBUILD option in the [OPTIONS] section of the HPJ file\r\n\r\nBUILD=expression\r\n\r\nYou specify the BUILD option in the [OPTIONS] section of the project (.hpj) file. You can use the BUILD option to include certain topics in and exclude them from the compiled Help file. The topics you include and exclude must contain the specified build tags. Use this option only if your topic (.rtf) files have build tags.\r\nA topic contains a build tag if it includes a build tag footnote (*). Topics without build tags are always compiled, regardless of the expression in the BUILD option.\r\n\r\nParameter - Description\r\n\r\nexpression - A logical statement that specifies which topics to include in or exclude from the build. This parameter consists of a combination of build tags (which must be specified in the [BUILDTAGS] section) and the following logical operators.\r\n\r\nOperator - Description\r\n~ Help Workshop compiles a topic only if the tag is not present. This operator has the highest precedence; Help Workshop applies it before any other operator.\r\n& Help Workshop compiles a topic only if it contains both build tags used in the expression. Help Workshop applies this operator only after the ~ operator has been applied.\r\n| Help Workshop compiles a topic if it has at least one of the build tags used in the expression. This operator has the lowest precedence; Help Workshop applies it only after all other operators have been applied.\r\n\r\nParentheses may be used to override operator precedence. Expressions enclosed within parentheses are always evaluated first.\r\n\r\nComments\r\n\r\nThe Help Workshop interface does not provide a way to specify the BUILD option in your project file. Instead, it provides a Build Tags tab in the Options dialog box that enables you to specify what build tags to include and exclude. These build tags are placed in the [INCLUDE] and [EXCLUDE] sections respectively. If there is an [INCLUDE] or [EXCLUDE] section in your project file when you compile a file, Help Workshop ignores any BUILD option you may have specified.\r\nTo use a BUILD option instead of an [INCLUDE] or [EXCLUDE] section, you must load the project file into a text editor and add the option to the [OPTIONS] section. You must also add a [BUILDTAGS] section specifying all the build tags that you will be using.\r\n\r\nOnly one BUILD option can be specified per project file.\r\nHelp Workshop evaluates all build expressions from left to right, using the specified precedence rules.\r\n\r\nExamples\r\n\r\nThe following examples assume that the [BUILDTAGS] section in the Help project defines the build tags DEMO, MASTER, and TEST_BUILD. Although the following examples show several BUILD options on consecutive lines using these build tags, only one BUILD option would be allowed in the project file.\r\n\r\nBUILD=DEMO ;Compile all topics that have the DEMO tag\r\nBUILD=DEMO & MASTER ;Compile all topics with both the DEMO and MASTER tag\r\nBUILD=DEMO | MASTER ;Compile all topics with either the DEMO or MASTER tag\r\nBUILD=(DEMO | MASTER) & TEST_BUILD ;Compile all topics that have either the DEMO or MASTER tag and also the TEST_BUILD tag\r\nBUILD=~ MASTER ;Compile all topics that do not have the MASTER tag",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:24:00",
"UpdatedBy": 0,
"Summary": "What are build tags and how do I use them?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1099,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Build Tags Causes a Topic to Lose Non-Scrolling Attribute",
"Symptoms": "The topic after a topic that I have excluded using build tags has lost it's non-scrolling attribute. This is a bug in the Microsoft Windows help compiler.",
"Resolution": "Insert an extra hard page break after each topic that is being excluded using build tags. You will still receive a warning about the non-scrolling region, but the non-scrolling region will be there.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:27:28",
"UpdatedBy": 0,
"Summary": "The topic after a topic that I have excluded using build tags has lost it's non-scrolling attribute.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1105,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Creating a Jump from an Authorable Button to a Secondary Window",
"Symptoms": "How can I create a jump from an authorable button to a secondary window?",
"Resolution": "Modify the JumpId macro that is created for you by putting a \">\" and the name of the secondary window you want the topic displayed in after the help file name. Example:\r\n{button test,JumpId(GENERIC.HLP>(w95sec),Help_Id)}",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:28:43",
"UpdatedBy": 0,
"Summary": "How can I create a jump from an authorable button to a secondary window?",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1107,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Authorable Button is Not Visible After Compiling",
"Symptoms": "After compiling my help project, I do not see my authorable button, just the {button ... } statement. If there is an error in the syntax of the button statement, the button will not be displayed. This is most commonly caused by the use of \"smart quotes\" in the text of the button statement.",
"Resolution": "Turn off smart quotes (Tools|Options|Auto Format, uncheck \"Convert straight quotes to smart quotes\") and retype the quotes in the {button ... } statement.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:30:08",
"UpdatedBy": 0,
"Summary": "After compiling my help project, I do not see my authorable button, just the {button ... } statement.",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1109,
"CategoryID": 0,
"NameID": 1,
"AreaID": 5,
"Title": "Syntax Error in the CNT File at line #",
"Symptoms": "This is generally caused by either a \">\" , a \"=\" before the \"=\" in the specified line in the .CNT file. It can also be caused by any non-alpha numeric character in the .CNT file.",
"Resolution": "Open the .CNT file in a text editor such as notepad and remove the offending character.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:31:24",
"UpdatedBy": 0,
"Summary": "Upon entering the Contents Tab Composer, I receive the message \"There is a syntax error in the CNT file at line linenumber.\"",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1111,
"CategoryID": 0,
"NameID": 1,
"AreaID": 5,
"Title": "Syntax Error in the .RTF File",
"Symptoms": "Upon entering the Contents Tab Composer, I receive the message \"There is a syntax error in the RTF file.\" This is caused by either Word Draw objects or Headers/Footers in the document.",
"Resolution": "Delete the Word Draw objects, remove the Headers/Footers, or just ignore this error message. It will not affect your .CNT file.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:32:32",
"UpdatedBy": 2,
"UpdatedOn": "02/06/97 18:14:35",
"Summary": "Upon entering the Contents Tab Composer, I receive the message \"There is a syntax error in the RTF file.\"",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1113,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Warning: This Version of CTL3D32.DLL is for Windows NT",
"Symptoms": "Upon entering RoboHELP, I receive the warning message \"This application uses CTL3D32.DLL, which is not the correct version. This version of CTL3D32.DLL is designed only for Windows NT systems.\"",
"Resolution": "Some application that you have installed recently has overwritten the Microsoft DLL CTL3D32.DLL, which RoboHELP uses. The DLL is actually displaying the error message, not RoboHELP. Rename CTL3D32.DLL in the Windows\\System directory to CTL3232.DLL, and re-install RoboHELP 4.00.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:33:43",
"UpdatedBy": 0,
"Summary": "I am receiving the warning \"This version of CTL3d32.DLL is for Windows NT.\"",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1115,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "What is the GID File?",
"Symptoms": "What is the GID file?",
"Resolution": "The GID file is a \"Contents database\" file, that is generated dynamically by the WinHelp 4.0 (Windows 95) help viewer (which is the help viewer for Windows 95 and Windows NT 3.51 and later). It contains an inventory of the HLP file. The GID file is a file that is automatically created by the WinHelp 4.0 (Windows 95) help viewer. This is a system/hidden file, so if you are using Windows NT, make sure File Manager is displaying hidden/system files (View menu|By File Type|check \"Show Hidden/System files). If you remove the CNT file, you need to delete this GID file. It will be automatically created the next time you run the help file. Any time that you are having difficulties with the \"Help Topics\" (Contents/Index/Find tabs) dialog box, the first thing you should try doing is deleting this GID file.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:35:15",
"UpdatedBy": 0,
"Summary": "What is the GID file?",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1117,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Error: Cannot Find File HELPFILE.CNT",
"Symptoms": "I get the error, cannot find file helpfile.cnt. This is generally caused by an out of date .GID file.",
"Resolution": "Delete the .GID file and run the help file again.\r\nSee Also: What is the GID file?",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:35:48",
"UpdatedBy": 0,
"Summary": "I get the error, cannot find file helpfile.cnt",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1120,
"CategoryID": 0,
"NameID": 1,
"AreaID": 10,
"Title": "Why are my Graphics Colors Shifing?",
"Symptoms": "When displaying graphics greater than 16 colors in my help file, the colors of the graphics in the running help file are not right. This is known as a palette shift. A palette shift can occur in any application that tries to display 256 color graphics on a computer that is running in 256 color mode. There are only 256 colors available in the palette when running in 256 color mode. Windows itself, the desktop, and any other application that is running are already using a certain number of those colors. There are not enough unique colors to display the graphic, so any color that can't be loaded is shifted to a color that is already in use.",
"Resolution": "Use graphics that only contain the standard Windows 16 colors (i.e. a 16 color bitmap) or have the users increase the color depth of their display adapters.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:37:16",
"UpdatedBy": 0,
"Summary": "My graphics colors are shifting.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1122,
"CategoryID": 0,
"NameID": 1,
"AreaID": 6,
"Title": "How to Localize a Help File for International Distribution?",
"Symptoms": "What do I need to do to localize my help file for international distribution?",
"Resolution": "Before turning the RoboHELP project over to the localization company, attach the \"normal.dot\" template to all of the DOC files in the project. Make sure that the \"Automatically update document styles\" box is NOT checked in the \"Templates and Add-Ins\" dialog.\r\nWhen you get the DOC's back from the localization Company, Reattach the RoboHELP templates to the documents. The main DOC in the project, the one with the same file name as the HPJ file, is attached to \"robohelp.dot\", all other documents in the project are attached to \"robortf.dot\".\r\nNote:If you are using RoboHELP 4.0 and creating a Windows 3.1 help project, the main document will be attached to robohp31.dot and all subordinate documents are attached to robort31.dot.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:38:24",
"UpdatedBy": 0,
"Summary": "What do I need to do to localize my help file for international distribution?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1124,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "RoboHELP 4.0 will not Recognize Windows 3.1 Help Project",
"Symptoms": "RoboHELP 4.0 checks the RBH file to determine if it is a Windows 3.1 or a Windows 95 help project. RoboHELP 4.0 will think that your Windows 3.1 help project is a RoboHELP 4.0 project if it finds the following in the RBH file:",
"Resolution": "1 Under the [Project] section you have the line:\r\nHelp Compiler=HCW.EXE\r\nIf this is the case, change the compiler name to HCP (no file extension)\r\n\r\n2 Under the [Project] section you have the line\r\nIncludeRTF=0\r\nIf this is the case, delete the line in it's entirety.\r\n \r\n3Under the [.RBH] section you have the line\r\n953PROJ=0\r\nIf this is the case, change the zero to a \"1\".\r\n\r\nEdit your .RBH file using a text editor, such as Notepad.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:39:59",
"UpdatedBy": 0,
"Summary": "I am trying to open my Windows 3.1 help project using RoboHELP 4.0, but RoboHELP will not recognize it as a Windows 3.1 project.",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1126,
"CategoryID": 0,
"NameID": 1,
"AreaID": 8,
"Title": "Displaying the Compatibility Wizard's Contents tab",
"Symptoms": "I want to display the Compatibility Wizard's Contents tab from my application. How do I do this?",
"Resolution": "To call the Compatibility Wizard from an application, use the WinHelp API. The help file must be opened first, that's why you see two WinHelp calls. The second call uses HELP_COMMAND, and the address of the string containing the macro to execute.\r\n\r\nvoid CTestView::OnTest() \r\n{\r\n char strbuf[] = \"HyperTopicsDMShowWindow()\";\r\n ::WinHelp(GetSafeHwnd(), \"generic.hlp\", HELP_CONTENTS, 0);\r\n ::WinHelp(GetSafeHwnd(), \"generic.hlp\", HELP_COMMAND, (DWORD) strbuf);\r\n}",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:44:18",
"UpdatedBy": 0,
"Summary": "I want to display the Compatibility Wizard's Contents tab from my application. How do I do this?",
"VersionStart": "3",
"VersionEnd": "3"
},
{
"KBID": 1130,
"CategoryID": 0,
"NameID": 1,
"AreaID": 11,
"Title": "There are Compiler Errors, but the Locate Button is Grayed Out. Why?",
"Symptoms": "I receive Microsoft help compiler errors, but the \"locate\" button is grayed out. Why? The locate button can only locate errors in the RTF files. Sometimes errors are in other files, such as .SHG files.",
"Resolution": "The error locator will take you to the beginning of the topic that contains the error. You can then search through the topic to find the actual error itself.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:46:05",
"UpdatedBy": 0,
"Summary": "I receive Microsoft help compiler errors, but the \"locate\" button is grayed out. Why?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1133,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "How Large Can My Help Project Be?",
"Symptoms": "How large can my help project be? How many topics should I have in each DOC file?",
"Resolution": "A Windows help file can be up to 2 gigabytes in size. \r\nWe recommend keeping your DOC files to 200 topics or less. This makes your projects easier to manage. You can have as many DOC files in your project as you wish.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:48:23",
"UpdatedBy": 0,
"Summary": "How large can my help project be? How many topics should I have in each DOC file?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1137,
"CategoryID": 0,
"NameID": 1,
"AreaID": 4,
"Title": "Paragraph Borders",
"Symptoms": "I am trying to add borders around my paragraphs, but in my final compiled help file I get a box around each line.",
"Resolution": "Use a newline character (shift+enter) rather than a paragraph mark (enter) to break up the lines.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:49:56",
"UpdatedBy": 0,
"Summary": "I am trying to add borders around my paragraphs, but in my final compiled help file I get a box around each line.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1139,
"CategoryID": 0,
"NameID": 1,
"AreaID": 4,
"Title": "Insert Symbol",
"Symptoms": "I am trying to insert a special symbol into my help file using the Insert Symbol feature inside of Word, but the character doesn't appear in my help file. Characters inserted by using Insert Symbol inside of Word do not appear in the final compiler help file",
"Resolution": "Use the character map utility to insert the character. \r\n\r\nWinHelp 3.1\r\nIn a Windows 3.1 help file, you can use any character from the lower 128 characters of any ASCII based font (i.e. Arial or Times New Roman) and the Symbol font.\r\n\r\nWinHelp 4.0 (Windows 95)\r\nIn a Windows 95 help file, you can use any character from the lower and extended characters of any ASCII based font, the Symbol font and the Wingding font.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:50:55",
"UpdatedBy": 0,
"Summary": "I am trying to insert a special symbol into my help file using the Insert Symbol feature inside of Word, but the character doesn't appear in my help file.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1143,
"CategoryID": 0,
"NameID": 1,
"AreaID": 11,
"Title": "Help compiler error 4010: There are more opening than closing braces in the RTF file.",
"Symptoms": "Microsoft Help compiler error 4010: There are more opening than closing braces in the RTF file. The RTF file may be corrupt. This is a bug in the Microsoft Windows 95 help compiler. This is most frequently caused by underlining in a bulleted list. The Microsoft Help Compiler is complaining about the format of the RTF file generated by Word 7.0, but it has no effect on the final compiled help file.",
"Resolution": "Look for underlining in bulleted lists (jumps in a bulleted list are commonly the cause of this error). It is nothing to be concerned about. You may ignore this error message.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:51:59",
"UpdatedBy": 0,
"Summary": "Microsoft Help compiler error 4010: There are more opening than closing braces in the RTF file. The RTF file may be corrupt.",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1145,
"CategoryID": 0,
"NameID": 1,
"AreaID": 8,
"Title": "Jumps from \"What's This?\" Help Topics Don't Work",
"Symptoms": "I have created \"What's This?\" Help topics with jumps, but the jumps don't work when the topic is called from the application. The Windows 95 help viewer does not support jumps or pop-ups from topics displaying \"What's This?\" or popup help topics called as context-sensitive help topics from an application.",
"Resolution": "The jumps will work if you use a JumpId or a PopupId macro.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:53:19",
"UpdatedBy": 0,
"Summary": "I have created \"What's This?\" Help topics with jumps, but the jumps don't work when the topic is called from the application.",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1147,
"CategoryID": 0,
"NameID": 1,
"AreaID": 10,
"Title": "How do I create a Tiled Bitmap?",
"Symptoms": "How do I create a tiled bitmap in the non-scrolling or scrolling region?",
"Resolution": "Use our DLL, HLP256.DLL, or HLP25632.DLL for WinHelp 4.0 (Windows 95) help files.\r\nWinHelp 3.1\r\nTile the graphic in the scrolling or non-scrolling region\r\n\r\nWinHelp 4.0 (Windows 95)\r\nTile the graphic in the scrolling or non-scrolling region",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:55:56",
"UpdatedBy": 0,
"Summary": "How do I create a tiled bitmap in the non-scrolling or scrolling region?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1149,
"CategoryID": 0,
"NameID": 1,
"AreaID": 8,
"Title": "Adding \"What's This?\" Style Help",
"Symptoms": "How do I add \"What's This?\" Style help to a Visual C++ MFC application? Context-sensitive help, including Windows 95 \"What's This?\" style help, is easy to add to your Visual C++ application.",
"Resolution": "The first step is to select the option for Context-sensitive Help in step 7 of the Visual C++ AppWizard. \r\n· For every dialog in the application, you must set the Extended dialog style \"Context Help\". \r\n· Every control in the dialog that you wish to provide \"What's This?\" style help should have the \"Help Id\" Property checked.\r\n· After compiling your Visual C++ application, a file will be created in your Visual C++ Application directory with the name resource.hm. This is the map file that you will use in your RoboHELP project to map the control identifiers to their corresponding help topics.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:57:35",
"UpdatedBy": 0,
"Summary": "How do I add \"What's This?\" Style help to a Visual C++ MFC application?",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1150,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Jumping to the Middle of a Topic from an Application",
"Symptoms": "How do I create a jump to the middle of a topic from an application?",
"Resolution": "First you need to insert a \"mid-topic context string\" at every position in the topic that you want to create a jump to. Insert these mid-topic context string by going to the Insert Menu, selecting Mid-topic context string, and give it a unique context string (it must not be the same as any other topic in the project).\r\nNow you must create a .HH file that lists these mid-topic context strings and their associated map numbers. RoboHELP does not automatically add mid topic context strings to the .HH file during automatic map file generation. Use a text editor such as notepad to create the .HH file in the same directory as the project, and follow the syntax of the other .HH files in the project. Each line in the .HH file should look like:\r\n#define mid_topic_context_string map#\r\n\r\nMake sure the map numbers are unique.\r\nNow include the new map file in the compile by going into Project Setup, Click on the Advanced tab, double click on the [MAP] section, highlight the new .HH file in the upper left hand window, and click on add to add it under Selected Files.\r\nNow when you compile, the mid-topic context strings will be mapped to the map id numbers that you specified. You can use these map id numbers to jump to that mid-topic context string from the application.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 13:59:55",
"UpdatedBy": 0,
"Summary": "How do I create a jump to the middle of a topic from an application?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1155,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "How Do I Allow Users to Print the Entire Help File?",
"Symptoms": "How do I give my user's the ability to print the entire help file?",
"Resolution": "WinHelp 3.1\r\nUse the WinHelp HyperViewer, which is available in WinHelp Office. It provides a hierarchical view of the help file, gives the user the ability to print some or all of the topics in the help file, and in combination with Find+, it adds full text search to your Windows 3.1 help files.\r\n\r\nWinHelp 4.0 (Windows 95)\r\nUse the Contents file. The user has the ability to print all of the pages under any one book.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 14:01:54",
"UpdatedBy": 0,
"Summary": "How do I give my user's the ability to print the entire help file?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1160,
"CategoryID": 0,
"NameID": 1,
"AreaID": 9,
"Title": "Macro Tips",
"Symptoms": "To insert a macro hotspot...\r\n1 Highlight the text you wish to use for your hotspot text.\r\n2 Go to the Insert menu and select Help Macro Hotspot.\r\n3 Click the Macro button in the lower right hand corner of the dialog.\r\n4 From the Choose a macro to Insert List, select the macro you wish to insert and click Insert.",
"Resolution": "Note: When specifying an absolute path in a WinHelp macro, you must always use either two backslashes \"\\\\\" or a single forward slash \"/\" instead of a single backslash in the path.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 14:03:40",
"UpdatedBy": 0,
"Summary": "Assorted Macro Tips",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1162,
"CategoryID": 0,
"NameID": 1,
"AreaID": 5,
"Title": "Help File Is Corrupt Error Message When I Click Run",
"Symptoms": "You are getting the error message because the Microsoft help compiler is still compiling the project in the background when you are clicking the Run button. In RoboHELP 4.0, we give an indication that the help project is still being compiled, but in the Contents Tab Composer, the compiling takes place in the background. If you click the Run button before the compile is finished, you will receive the error message.",
"Resolution": "Wait until the Compile is complete before clicking the run button.\r\nNote: Under Windows 95, you can see the Help Compiler HCW on the task bar when it is compiling. Under Windows NT, you will have to Alt-Tab to display the background help compiler process.",
"CreatedBy": 2,
"CreatedOn": "02/04/97 14:04:27",
"UpdatedBy": 0,
"Summary": "I am compiling my project in the Contents Tab Composer, but when I click Run, I get a message that the help file is corrupt.",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1169,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Error 177: Cannot Display Find Tab",
"Symptoms": "Error 177: Cannot Display Find tab is usually caused by one of the following problems:\r\n· The Microsoft Help Viewer does not have enough free disk space to create FTS file.\r\n· Out of date GID file.\r\n· Link to HLP file with no keywords.",
"Resolution": "This is generally caused by an out of date .GID file. Delete the .GID file and run the help file again.\r\n\r\nSee Also: What is the GID file?",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:13:02",
"UpdatedBy": 0,
"Summary": "I am running my help file and I receive Error 177: Cannot Display Find tab",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1170,
"CategoryID": 0,
"NameID": 1,
"AreaID": 4,
"Title": "How Do I Make My Table Fit the Size of the Help Window?",
"Symptoms": "How do I make my table autofit the size of the help window?",
"Resolution": "Center the table in your Word document. Put your cursor somewhere inside of the table. From the Table menu, select \"Select Table\". Then from the Table menu, select \"Cell Height and Width\". Click the Row tab, and select \"Center\" under Alignment. Click OK.\r\n \r\nMake each column width the minimum size that you want to display. This will be the smallest size the window can be reduced to before the user gets \"scroll bars\" and the table will not fit on the screen.\r\n\r\nAs the user widens the Help window, the table will widen, and the text will flow to fit the new column widths.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:14:37",
"UpdatedBy": 0,
"Summary": "How do I make my table autofit the size of the help window?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1179,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Unable to Compile Windows 3.1 Help Projects",
"Symptoms": "I have installed RoboHELP under a directory with a space in it, and now I can't compile my Windows 3.1 help projects. The Microsoft Help Compiler is an MS-DOS based program, and cannot execute from a directory if it contains a space or a long file name in the path.",
"Resolution": "Install RoboHELP to a directory that has no spaces and in eight characters or less.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:15:55",
"UpdatedBy": 0,
"Summary": "I have installed RoboHELP under a directory with a space in it, and now I can't compile my Windows 3.1 help projects.",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1182,
"CategoryID": 0,
"NameID": 1,
"AreaID": 8,
"Title": "Using the HM File from a Developer in My Help Project",
"Symptoms": "How do I use the .hm file from my developer in my RoboHELP project?",
"Resolution": "· Open a new RoboHELP Windows 95 help project. Give the HPJ file the same name as your application. Under Development Environment, select your environment. \r\n· Copy the .hm file from you application directory to your RoboHELP project directory.\r\n· Inside of your RoboHELP project, go into Project Setup, click the Advanced tab, and double click on the MAP section. The .hm file will be listed in the upper left hand window in the \"Choose Files For\" dialog. Select it and click Add. It will be added under \"Selected Files\" in the lower window. Click OK.\r\n· Create your overview and procedural help topics. We will connect these topics with the Visual C++ .hm map file using the alias section of the HPJ file, with the help of the RoboHELP Contents Tab Composer.\r\n· To create new \"What's This?\" style topics:\r\n1 Click the \"Create Popup\" button and select the \"New What's This?\" tab, creating a context-sensitive topic to display in a What's This? style popup window\r\n2 Click Choose.\r\n3 The Choose Topic ID Provided by Development Team dialog box appears.\r\n4 Click Browse to select a map file. \r\n5 Select the correct Topic ID.\r\n6 Click OK.\r\n7 Enter the definition text for the Help topic in the space provided.\r\n8 Click OK.\r\nTIP: If possible, place all context-sensitive Help topics in one document. This means that you can use the automatic map file generation for the entire Help document. This saves time in creating or assigning specific map numbers for all context-sensitive topics within various Help documents. \r\n\r\nNote: What's This? style topics do not generally have a ? character contained in their footnotes. Instead, these topics contain only the # character.\r\n· Copy the HLP file to the same folder as your application.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:18:05",
"UpdatedBy": 0,
"Summary": "How do I use the .hm file from my developer in my RoboHELP project?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1184,
"CategoryID": 0,
"NameID": 1,
"AreaID": 11,
"Title": "Help Compiler Error 1230: File filename not found.",
"Symptoms": "Microsoft Help Compiler Error 1230: File filename not found indicates that the Microsoft Help compiler cannot find the specified file.",
"Resolution": "Make sure the file name is properly listed, of removed if the file was intentionally deleted, in the project file.\r\nGo into Project Setup and click on the advanced tab.\r\nFor .RTF files: Double click on the [FILES] section\r\nFor .HH or other map files: Double click on the [MAP] section\r\nFor Graphic files: Double click on the BMROOT= section\r\nVerify that the proper files, with the proper drives and paths, are listed under Selected Files (or Selected Directories).\r\nClick OK and recompile.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:19:19",
"UpdatedBy": 0,
"Summary": "When compiling I am receiving Microsoft Help Compiler Error 1230: File filename not found.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1188,
"CategoryID": 0,
"NameID": 1,
"AreaID": 8,
"Title": "Context-Sensitive Help under Windows NT",
"Symptoms": "Under Windows NT (as well as Win 32s), 16 bit applications call the 16-bit help viewer, winhelp.exe, and 32-bit applications call the 32-bit help viewer, winhlp32.exe. \r\n\r\nA 32-bit application can call a Windows 3.1 help file without a problem, as long as that help file does not use any 16-bit DLL's.",
"Resolution": "It the Windows 3.1 help file does use 16-bit DLL's, a notification message will displayed telling the user the WinHelp is switching to the 16-bit help viewer. The context-sensitive topic information is lost during this transfer. 32-bit applications can not call Windows 3.1 help file that use 16 bit DLL's. They can call them if they do not use 16-bit DLL's.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:22:54",
"UpdatedBy": 0,
"Summary": "I am creating a context-sensitive help file to run under Windows NT. What do I need to be aware of?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1190,
"CategoryID": 0,
"NameID": 1,
"AreaID": 9,
"Title": "Unable to Insert an Item into the Help Menu",
"Symptoms": "I want to insert an item into the help menu, but it's not working. This occurs because the menu id is incorrectly listed in both the Microsoft and the RoboHELP documentation.",
"Resolution": "The menu id should be mnu_help, not mnu_helpon.\r\nThis can also cause an \"Unable to add menu item\" error message occurs when trying to add a menu item to the Windows Help engine's Help menu with InsertItem().",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:23:52",
"UpdatedBy": 0,
"Summary": "I want to insert an item into the help menu, but it's not working.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1192,
"CategoryID": 0,
"NameID": 1,
"AreaID": 9,
"Title": "What are the Virtual Key Codes for the AddAccelerator Macro?",
"Symptoms": "What are the Virtual Key Codes for AddAccelerator macro?",
"Resolution": "=====From HCW.HLP=====\r\nParameter - Description\r\nkey: Specifies the Windows virtual-key value. This parameter can be a numeric digit, a quoted character (as in `A'), or one of the following strings:\r\n\r\nVK_LBUTTON VK_NUMPAD2\r\nVK_RBUTTON VK_NUMPAD3\r\nVK_CANCEL VK_NUMPAD4\r\nVK_MBUTTON VK_NUMPAD5\r\nVK_BACK VK_NUMPAD6\r\nVK_TAB VK_NUMPAD7\r\nVK_CLEAR VK_NUMPAD8\r\nVK_RETURN VK_NUMPAD9\r\nVK_SHIFT VK_MULTIPLY\r\nVK_CONTROL VK_ADD\r\nVK_MENU VK_SEPARATOR\r\nVK_PAUSE VK_SUBTRACT\r\nVK_CAPITAL VK_DECIMAL\r\nVK_KANA VK_DIVIDE\r\nVK_KANJI VK_F1\r\nVK_HANGEUL VK_F3\r\nVK_JUNJA VK_F5\r\nVK_HANJA VK_F6\r\nVK_ESCAPE VK_F7\r\nVK_SPACE VK_F8\r\nVK_PRIOR VK_F9\r\nVK_NEXT VK_F10\r\nVK_END VK_F11\r\nVK_HOME VK_F12\r\nVK_LEFT VK_F13\r\nVK_UP VK_F14\r\nVK_RIGHT VK_F15\r\nVK_DOWN VK_F16\r\nVK_SELECT VK_F17\r\nVK_PRINT VK_F18\r\nVK_EXECUTE VK_F19\r\nVK_SNAPSHOT VK_F20\r\nVK_INSERT VK_F21\r\nVK_DELETE VK_F22\r\nVK_HELP VK_F23\r\nVK_SCROLL VK_F24\r\nVK_NUMPAD0 VK_NUMLOCK\r\nVK_NUMPAD1\r\n\r\nshift-state: Specifies the combination of ALT, SHIFT, and CTRL keys to be used with the accelerator. This parameter can be one of the following values:\r\n\r\nNONE (0)\r\nSHIFT (1)\r\nCTRL (2)\r\nSHIFT+CTRL (3)\r\nALT (4)\r\nALT+SHIFT (5)\r\nALT+CTRL (6)\r\nSHIFT+ALT+CTRL (7)",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:25:39",
"UpdatedBy": 0,
"Summary": "What are the Virtual Key Codes for AddAccelerator macro?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1196,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Author Defined Background Colors are not Showing Up.",
"Symptoms": "If the default background color of the main window is anything other than white, the user's desktop color scheme will override the author defined colors for the scrolling and non-scrolling regions in the help file.",
"Resolution": "There is no workaround for this behavior. The Windows help viewer was designed this way by Microsoft.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:28:54",
"UpdatedBy": 0,
"Summary": "My author defined background colors are not showing up.",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1198,
"CategoryID": 0,
"NameID": 1,
"AreaID": 8,
"Title": "WinHelp API Function",
"Symptoms": "What are the parameters and Values for the WinHelp API function? The WinHelp function starts Windows Help (WINHELP.EXE) and passes additional data indicating the nature of the help requested by the program.",
"Resolution": "=====From HCW.HLP=====\r\n\r\nWinHelp\r\n\r\nBOOL WinHelp(HWND hwnd, LPCTSTR lpszHelpFile, UINT fuCommand, DWORD dwData)\r\n\r\nThe WinHelp function starts Windows Help (WINHELP.EXE) and passes additional data indicating the nature of the help requested by the program.\r\n\r\nParameter Description\r\n\r\nhwnd: Handle of the window requesting Help. The WinHelp function uses this handle to keep track of which programs have requested Help. If fuCommand specifies HELP_CONTEXTMENU or HELP_WM_HELP, hwnd identifies the control requesting Help.\r\nlpszHelpFile: Address of a null-terminated string containing the path, if necessary, and the name of the Help file that WinHelp is to display.\r\nThe filename may be followed by an angle bracket (>) and the name of a secondary window if the topic is to be displayed in a secondary window rather than in the primary window. The name of the secondary window must have been defined previously in the [WINDOWS] section of the Help Project (.HPJ) file.\r\n\r\nfuCommand: Type of help requested. For a list of possible values and how they affect the value to place in the dwData parameter, see the Comments section.\r\ndwData: Additional data. The value used depends on the value of the fuCommand parameter. For a list of possible values, see the Comments section.\r\n\r\nReturn Value\r\n\r\nIf successful, the return value is TRUE; otherwise, it is FALSE.\r\n\r\nComments\r\n\r\nThe program specifies the name and, where required, the directory path of the Help file to display.\r\nBefore closing the window that requested Help, the program must call WinHelp with the fuCommand parameter set to HELP_QUIT. Until all programs have done this, WinHelp will not terminate. Note that calling WinHelp with the HELP_QUIT command is not necessary if you used the HELP_CONTEXTPOPUP command to start Help.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:30:16",
"UpdatedBy": 0,
"Summary": "What are the parameters and Values for the WinHelp API function?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1200,
"CategoryID": 0,
"NameID": 1,
"AreaID": 8,
"Title": "How Can I Test My Context Sensitive Help File?",
"Symptoms": "How can I test my context-sensitive help file from the command line?",
"Resolution": "Go to the Start button, select run, and type in:\r\nwinhelp -n map# name\r\nwhere map# is the id number that you want to test in the help file and name is the full path and name of the help file you want to test. For example, to test map # 101 in generic.hlp in the RoboHELP directory, type in\r\nwinhelp -n 101 c:\\robohelp\\generic.hlp\r\nTo check the number the application is sending to the help file, go to the RH95 directory, double click on HCW.EXE, go to the View menu and select WinHelp messages. Run the application. HCW will report the ID number the app is sending to the help file.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:32:58",
"UpdatedBy": 0,
"Summary": "How can I test my context-sensitive help file from the command line?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1202,
"CategoryID": 0,
"NameID": 1,
"AreaID": 8,
"Title": "Troubleshooting a Context-Sensitive Help File",
"Symptoms": "Verify the Map File is included in the project properly by testing the help file from the command line.\r\nIf testing brings up the appropriate map number, then the problem is up to the application developer's.",
"Resolution": "If testing does not bring up the appropriate help topic, the error is in the help file. This can be caused by:\r\n1 Not including the map file in the [MAP] section of the project (.HPJ) file.\r\n2 An invalid map (.hh) file.\r\n3 Compile errors.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:33:42",
"UpdatedBy": 0,
"Summary": "How do I troubleshoot my context-sensitive help file?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1204,
"CategoryID": 0,
"NameID": 1,
"AreaID": 9,
"Title": "Running a Macro from the CNT Tab or SHED Editor",
"Symptoms": "How do I run a macro from the Contents tab or the SHED editor?",
"Resolution": "When running a macro from the Contents tab or as a macro in a .SHG file, you must use the short name of the macro, include parameters (non-numeric) in quotation marks, and include all required parameters.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:34:49",
"UpdatedBy": 0,
"Summary": "How do I run a macro from the Contents tab or the SHED editor?",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1206,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Warning: \"MyFile.doc\" is not a member of the current project",
"Symptoms": "When accessing a RoboHELP function, I receive the warning \"filename.doc\" is not a member of the current project.",
"Resolution": "Make sure filename is correct in the [FILES] section of the .HPJ file. Go to Project Setup, click the advanced tab, and verify the proper path to the .RTF file is listed under selected files.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:36:25",
"UpdatedBy": 0,
"Summary": "When accessing a RoboHELP function, I receive the warning \"filename.doc\" is not a member of the current project.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1211,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "Jumps to a Mid-Topic ID go to the Topic Title",
"Symptoms": "I'm trying to create a jump to a mid-topic Topic Id, but it continues to go to the topic title. What's wrong? Jumps to mid-topic topic id's are not supported in auto-sizing secondary windows.",
"Resolution": "Change the Windows attribute so it is no longer auto-sizing. \r\n1 Go to Project Setup\r\n2 Click the Advanced tab\r\n3 Double click on the [WINDOWS] section\r\n4 Double click on the window that you want to edit.\r\n5 Uncheck \"Auto-Size Height\"",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:37:31",
"UpdatedBy": 0,
"Summary": "I'm trying to create a jump to a mid-topic Topic Id, but it continues to go to the topic title. What's wrong?",
"VersionStart": "4",
"VersionEnd": "4"
},
{
"KBID": 1215,
"CategoryID": 0,
"NameID": 1,
"AreaID": 4,
"Title": "How do I spell check my project?",
"Symptoms": "How do I spell check my project?",
"Resolution": "Make a back up of the document that you will be working on.\r\n· Turn off \"Hidden Text\"\r\n· Spell check the document\r\n· In certain circumstances, modifications to the RoboHELP templates make Word unable to spell check a RoboHELP document. Attach the normal.dot template to the document, run the spell check, and then re-attach the appropriate RoboHELP document template.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:39:13",
"UpdatedBy": 0,
"Summary": "How do I spell check my project?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1217,
"CategoryID": 0,
"NameID": 1,
"AreaID": 6,
"Title": "Converting to OS/2",
"Symptoms": "One Up Corporation, provides services for migrating Windows C and C++ apps to 32-bit OS/2. It can also convert RTF files into IPF files (the source files for OS/2's help).",
"Resolution": "For more information, contact:\r\n\r\nOne Up Corporation\r\n1603 LBJ Freeway\r\nSuite 200\r\nDallas. TX 75234\r\n800.678.0187 or fax 214.620.9626",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:40:10",
"UpdatedBy": 0,
"Summary": "Converting to OS/2",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1219,
"CategoryID": 0,
"NameID": 1,
"AreaID": 6,
"Title": "Converting to UNIX",
"Symptoms": "For information about porting Windows help files to UNIX, contact Bristol Technology. They make a program called HyperHelp which will convert your Windows help files to on-line UNIX help.",
"Symptoms": "For information about porting Windows help files to the Macintosh, contact Altura Software. They make a program called QuickHelp. QuickHelp is a WinHelp compiler/viewer for the Mac that lets you use your existing HPJ and RTF files.",
"Resolution": "Altura Software \r\n510 Lighthouse Road.\r\nSuite 5\r\nPacific Grove, CA 93950\r\nphone: 408.655.8005\r\nfax: 408.655.9663\r\nquickhelp@altura.com",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:41:43",
"UpdatedBy": 0,
"Summary": "Converting to Macintosh",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1223,
"CategoryID": 0,
"NameID": 1,
"AreaID": 2,
"Title": "Adding a Help document to a Help project",
"Symptoms": "Adding a Help document to a Help project",
"Resolution": "1.Open a Help document. \r\n2.Click Setup Project in the RoboHELP tool palette.\r\n3.On the Settings tab, click Document.\r\n4.Select the document you want to include in the Help project. If the document you want to include is not listed, do the following:\r\n* In Drives, select a new drive.\r\n* In Directories, select a new directory.\r\n* Click Add. \r\nThe name of the shared Help document should be listed in Selected Files.\r\n5.Click OK.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:42:26",
"UpdatedBy": 0,
"Summary": "Adding a Help document to a Help project",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1225,
"CategoryID": 0,
"NameID": 1,
"AreaID": 4,
"Title": "Which RoboHELP Template should be Attached to my Document?",
"Symptoms": "RoboHELP uses two different templates in each project. One template is attached to the main document in the project (the one with the same name as the .HPJ file) and the other is attached to all other documents. The name of the template attached to a document is important in a RoboHELP project. It allows RoboHELP to determine which .HPJ file to use for a project.",
"Resolution": "To attach a different template to a document, from the File menu, select Templates…, click the Attach button, and select the template that you want to attach to the document. \r\n\r\nNote: No RoboHELP templates should be listed under Global Templates and Add-ins. If they are, remove them.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:43:54",
"UpdatedBy": 0,
"Summary": "Which RoboHELP template should be attached to my document?",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 3000,
"CategoryID": 0,
"NameID": 2,
"AreaID": 12,
"Title": "Under Construction",
"Symptoms": "Under Construction",
"Resolution": "Under Construction",
"CreatedBy": 3,
"CreatedOn": "02/04/97 18:01:49",
"UpdatedBy": 4,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "Just some additional help topics to use multiple products.",
"VersionStart": "0",
"VersionEnd": "0"
},
{
"KBID": 3001,
"CategoryID": 0,
"NameID": 3,
"AreaID": 13,
"Title": "Under Construction",
"Symptoms": "Under Construction",
"Resolution": "Under Construction",
"CreatedBy": 3,
"CreatedOn": "02/04/97 18:01:49",
"UpdatedBy": 4,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "Just some additional help topics to use multiple products.",
"VersionStart": "0",
"VersionEnd": "0"
},
{
"KBID": 1186,
"CategoryID": 0,
"NameID": 1,
"AreaID": 2,
"Title": "When Editing Topics I Get the Title for the Next Topic",
"Symptoms": "I have imported a help file from another authoring tool, and when I edit the topics, I get the title for the next topic, instead of the current one.",
"Resolution": "RoboHELP expects the order of the footnotes to be \"# $ K +\". Change the order of the footnotes in the help document to be \"# $ K +\" and RoboHELP will display the correct topic information.",
"Notes": "Checking the last updated fields",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:21:08",
"UpdatedBy": 0,
"UpdatedOn": "02/06/97 15:51:29",
"Summary": "I have imported a help file from another authoring tool, and when I edit the topics, I get the title for the next topic, instead of the current one.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1079,
"CategoryID": 0,
"NameID": 1,
"AreaID": 3,
"Title": "When Compiling, I am Prompted to Create a Skeletal HPJ",
"Symptoms": "When I compile my help project, RoboHELP tells me there is no HPJ, and it will create a skeletal HPJ file for me. I do have an HPJ file.",
"Resolution": "One or more of the DOC files in your project are attached to the wrong template. The main DOC file (the one with the same name as the HPJ file) must be attached to the robohelp.dot template. All other DOC files in the Help project must be attached to the robortf.dot template. To attach a template, from the File menu, choose Templates and click the Attach button. \r\nNote:If you are using RoboHELP 4.00a and creating a Windows 3.1 help project, the main document will be attached to robohp31.dot and all subordinate documents are attached to robort31.dot.",
"CreatedBy": 1,
"CreatedOn": "02/04/97 13:11:22",
"UpdatedBy": 2,
"UpdatedOn": "02/06/97 00:00:00",
"Summary": "When I compile my help project, RoboHELP tells me there is no HPJ, and it will create a skeletal HPJ file for me. I do have an HPJ file.",
"VersionStart": "3",
"VersionEnd": "4"
},
{
"KBID": 1166,
"CategoryID": 0,
"NameID": 1,
"AreaID": 8,
"Title": "Displaying the Help Topics Dialog from an Application",
"Symptoms": "How do I display the Help Topics dialog box from my application?",
"Resolution": "To display the Help Topics dialog in the last state that it was accessed:\r\nvoid CTestView::OnHelpFinder() \r\n{\r\n ::WinHelp(GetSafeHwnd(), \"generic.hlp\", HELP_FINDER, 0);\r\n}\r\n\r\nTo display the Help Topics dialog with the Contents tab displayed (note: this is not documented by Microsoft):\r\nvoid CTestView::OnHelpContents() \r\n{\r\n ::WinHelp(GetSafeHwnd(), \"generic.hlp\", 15, 0);\r\n}\r\n\r\nTo display the Help Topics dialog with the Index tab displayed:\r\nvoid CTestView::OnHelpIndex() \r\n{\r\n char strbuf[] = \"\";\r\n ::WinHelp(GetSafeHwnd(), \"generic.hlp\", HELP_PARTIALKEY, (DWORD) strbuf);\r\n}",
"Notes": "The summary and symptoms on this topic could really be improved.",
"CreatedBy": 3,
"CreatedOn": "02/04/97 14:11:41",
"UpdatedBy": 0,
"Summary": "How do I display the Help Topics dialog box from my application?",
